Method and apparatus for identifying wireless access points using beacon frames

ABSTRACT

Techniques are described for identifying a wireless access point device using beacon messages and probe responses. An access point may generate and broadcast beacon messages which include an information element containing information specific to the device as well as to the current context of the device. For example, the information element may include a device vendor ID, product ID, and a device-unique ID. That is, the information element provides information related to the device itself independently from the configuration of the wireless network which the beacon message (or probe response) is associated with.

TECHNICAL FIELD

Embodiments presented herein generally relate to computer networkingdevices. More specifically, embodiments presented herein providetechniques for identifying a wireless access point hosting one or morewireless networks.

BACKGROUND

Wireless networks have become commonplace. For example, wireless accesspoints are used in both home and enterprise environments to provide aninternet connection to a variety of Transport Control Protocol/InternetProtocol (TCP/IP) enabled devices. The access points typically operateusing a version of the IEEE 802.11 wireless local area network protocol(e.g., the 802.11a, b, g or n versions of this protocol). Desktop PCs,laptop PCs, mobile telephones, VoIP telephones, tablets, net-books,video game consoles, digital video recorders, DVD players, videostreaming systems, among other devices, can connect to wireless networksoperating according to these standards.

To associate itself with a wireless network, a host station typicallyidentifies a service set identifier (SSID) broadcast by an access pointand then performs a process defined by the 802.11 protocol to join thewireless network corresponding to that SSID. Users may also need tosupply credentials (e.g., a password or PKI certificate) in order toassociate a host station with a wireless network. Wireless access pointstypically broadcast a variety of management frames. Management framesallow hosts to obtain information used to send a request to attach tothe wireless network, e.g., to obtain information used to generate aDynamic Host Configuration Protocol (DHCP) request for an internetprotocol address. Similarly, a beacon frame may be used by wirelessdevices to identify a network configured on the wireless access point.Beacon frames are broadcast over regular periodic intervals, allowingnew devices to associate to the wireless network as well as providinginformation to already associated hosts.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the features the embodiments presentedherein can be understood in detail, a more particular description may behad by reference to example embodiments, some of which are illustratedin the appended drawings. It is to be noted, however, that the appendeddrawings illustrate only example embodiments and are therefore not to beconsidered limiting of its scope.

FIG. 1 illustrates an example computing environment which includes awireless access point, according to one embodiment presented in thisdisclosure.

FIG. 2 further illustrates the wireless access point and a computingsystem first illustrated in FIG. 1, according to one embodimentpresented in this disclosure.

FIG. 3A illustrates an example format for data frames broadcast from awireless access point in order to identify that wireless access point,according to one embodiment presented in this disclosure.

FIG. 3B illustrates an example format for data frames broadcast from awireless access point in order to identify that wireless access point,according to one embodiment presented in this disclosure.

FIG. 4 illustrates a method for a wireless access point to broadcastframes used to identify that wireless access point, according to oneembodiment presented in this disclosure.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

One embodiment includes a computer-implemented method. This method maygenerally include exposing, on a wireless access point device, at leasta first wireless network and also include generating a first managementframe corresponding to the first wireless network. The management frameincludes an information element storing a plurality of informationfields. The information fields store information related to the wirelessaccess point device that is independent from a configuration of thefirst wireless network. The management frame includes an informationelement storing a plurality of information fields storing informationrelated to the wireless access point device that is independent of aconfiguration of the first wireless network exposed on the wirelessaccess point device. This method also includes broadcasting themanagement frame to one or more client devices within range of thewireless access point.

Other embodiments include, without limitation, a computer-readablemedium that includes instructions that enable a processing unit toimplement one or more aspects of the disclosed methods as well as asystem configured to implement aspects of the disclosed methods.

Example Embodiments

While a beacon frame may provide information about a network configuredon an access point, access point configurations can change over time.Further, most access points can be “factory reset,” restoring a defaultconfiguration state to an access point. As a result, it can be difficultto identify a specific access point from the various management framesbroadcast by an access point, other than through a Media Access Control(MAC) address. However, a single physical access point can providevirtual access points (VAPs) via virtualization and radio bandwidthdifference. In such cases, each VAP may use a different MAC address.Each VAP provides an access point with its own distinct networkconfiguration—as though there were two (or more) physical access pointsin a given environment. Each VAP may be identified by a beacon or proberesponse, but does not provide information indicating that the virtualaccess points are on a single device. Further still, the managementframes provide little information about device context.

Embodiments presented herein provide a wireless access point configuredto broadcast management or beacon frames which convey identity andcontext information to devices within broadcast range. Doing so allowsconfiguration software to distinguish one access point from another, aswell as identify when multiple VAPs are hosted by a common physicaldevice. In one embodiment, the access point may encode device-specificinformation in an information element broadcast as part of a basicservice set (BSS) beacon of a wireless interface on an access point. Theinformation elements may allow clients to discover devices withoutneeding to establish a connection or associate to a network on theaccess point. Instead, the client simply observes the beacon frames.Further, this approach allows the information element to be broadcastwithout interfering or conflicting with well-established wirelessnetworking standards; namely, the suite of 802.11 protocols.

Further still, doing so allows multiple virtual access points to beidentified as being hosted on a common access point as well as thestate/context of each virtual access point to be determined. Thispermits easy discovery of a desired device as well as easy rediscoveryof a previously connected device across settings changes which alter theidentifiable attributes of the BSS beacon or probe response frames.

In one embodiment, the information element may contain informationspecific to both the configuration and current context of the device.For example, the information element may include a device vendor ID,product ID, and a device-unique ID. This information element may alsoinclude a version field used to identify a version of firmware orapplications running on the device. This may be useful for discerningdevice compatibility—allowing a configuration or setup application toenable (or disable) certain configuration features depending on theirsupport on the device.

The information element may also include context specific informationregarding a device's configuration or state. The context information mayprovide the client with device and/or access point specific information,e.g., whether a device is configured or factory reset or whether a VAPis acting as a guest, configuration, or primary wireless network on awireless access point. The context information could also provide anindication of load or utilization for the access point. Doing so wouldallow a client in an environment with multiple access points (or asingle access point with multiple radios) to account for congestion at agiven access point when selecting one of the access points to associateto. Thus, in addition to identifying an access point and its state forsetup purposes, the context information can include additionalinformation in the beacon signal, allowing clients to make intelligentdecisions based on performance.

Similarly, the context information may indicate what features aresupported. That is, the context information could provide an indicationof supported features such as geolocation services or QRCode support. Asanother example, the context information could also indicate the statusof an upstream link on the access point. For example, if an access pointno longer has upstream WAN access, then it can turn off the WAN/internetbit in a context information field to signal to clients that it does notcurrently have access. This is useful for mobile hotspots where relianceon another radio may mean that internet access may vary.

Thus, using the BSS frame of a beacon or probe response, an informationelement specific to the identity of the device may permit clients toidentify the access point (or access points) they are looking for. Withthe client knowing the identity of a given access point, the client maytrack the device via beacons and probe responses across settings changesand factory resets as well as observe a variety of configuration andcurrent state context information about the device.

Note, the following description describes embodiments implemented in amanner that integrates with the existing 802.11 standards. However, oneof ordinary skill in the art will recognize that embodiments presentedin this disclosure can be generally applicable and extensible to otherwireless networking protocols or network infrastructures. That is, thetechniques presented herein may be adapted for use with other wirelessnetworking infrastructures where one device advertises itself to clientsusing a beacon (or other) management frames.

FIG. 1 illustrates an example computing environment 100 which includes awireless access point 120 configured according to one embodimentpresented in this disclosure. As shown, the computing environment 100includes a wireless access point 120 which provides an uplink to anetwork 105 (e.g., the internet) for a plurality of wireless clients 130₁₋₂. Illustratively, two such clients 130 ₁₋₃ have established aconnection to a wireless network hosted by the access point 120.Specifically, a mobile device 130 ₁ and a computing system 130 ₂. Theclient devices 130 ₁₋₂ each include a transceiver and antenna 137 ₁₋₂used to exchange modulated RF signals with the access point 120.

Mobile device 130 ₁ is included to be representative of a variety ofhandheld computing devices such as a mobile telephone or “Smartphone,”handheld computing tablet, video game and a digital music/video players,etc. As shown, the mobile device 130 ₁ network interface 135 ₁ used toconnect the mobile device 1301 to a network hosted by the wirelessaccede point. Network interface 135 ₁ may include the appropriatehardware and software modules used to send/receive network framescomposed according to one of the 802.11 networking protocol standards.

Similarly, computing system 130 ₂ is included to be representative of adesktop, laptop, or other computer. Accordingly, computing system 130 ₂may include a processor, memory, and storage device, along with theappropriate computing peripherals (e.g., a network interface 135 ₂,display, keyboard, mouse, etc.). Like the mobile device 130 ₁ networkinterface 135 ₂ may include the appropriate hardware and softwaremodules used to send/receive network frames composed according to one ofthe 802.11 networking protocol standards.

In one embodiment, the wireless access point 120 exposes one or morewireless networks. That is, once a wireless network is configured, theaccess point 120 exposes it to clients, allowing clients to associatethemselves with that network. As shown, a beacon message 115 has beenbroadcast from the wireless access point 120. In one embodiment, thehost station (i.e., mobile device 130 ₁ and computing system 130 ₂)receive beacon messages 115 from each access points within rangeadvertising their SSIDs (including a beacon for each virtual accesspoint configured on wireless access point 130. That is, each networkexposed by the wireless access point 120 may be identified through theadvertised SSID beacons. The client devices can then either manually orautomatically—based on configuration—select a wireless to network toassociate with or join. Further, in one embodiment, the beacon message115 may include an information element used to provide device specificinformation (e.g. a device vendor, product, and device ID) along withcurrent context information regarding the device's current state orconfiguration. Doing so allows applications on the computing system(e.g., configuration software) to determine whether the beacons arebeing broadcast from separate devices or from multiple virtual accesspoints on a single device. Further, the information element could allowthe configuration software to identify a device that has been previouslyconfigured via that software application but subsequently reset to afactory default state. In such a case, the software could offer torestore prior network configuration settings. Similarly, including adevice-specific information element in the beacon message 115 allows theconfiguration software to identify a specific access point in anenvironment where multiple access points are present—e.g., in anenterprise setting where multiple devices are broadcasting the same SSIDor in a residential apartment building where multiple devices (andbeacon messages 115) are visible to the configuration software.

A host station (i.e., mobile device 130 ₁ and computing system 130 ₂)may also send a probe request frame to trigger a probe response when thestation needs to obtain information from another station. For example, ahost station broadcasts a probe request when using active scanning todetermine which access points are within range for possible association.As with the beacon message 115, in one embodiment, a probe responsemessage may include an information element used to provide devicespecific information (e.g. a device vendor, product, and device ID)along with current context information regarding the device's currentstate or configuration. That is, in addition to the periodic beaconmessage 115, which broadcasts the information element at regularintervals, a host station may also send a probe request, which resultsin the wireless access point generating a response which includes theinformation element used to identify a given access point 120.

FIG. 2 further illustrates the wireless access point 120 and a computingsystem 130 ₂ first illustrated in FIG. 1, according to one embodimentpresented in this disclosure. As shown, the computing system 130 ₂includes, without limitation, a central processing unit (CPU) 205, anetwork interface 215, an interconnect 220, a memory 225, and storage230. The computing system 130 ₂ also includes an I/O device interface210 connecting I/O devices 212 and a display 214 to the computing system140 (e.g., a keyboard, mouse, and display screen).

The CPU 205 retrieves and executes programming instructions stored inthe memory 225. Similarly, the CPU 205 stores and retrieves applicationdata residing in the memory 225. The interconnect 220 facilitatestransmission, such as programming instructions and application data,between the CPU 205, I/O devices interface 210, storage 230, networkinterface 215, and memory 225. CPU 205 is included to be representativeof a single CPU, multiple CPUs, a single CPU having multiple processingcores, and the like. The memory 225 is generally included to berepresentative of a random access memory. The storage 230 may be, e.g.,a disk drive or a solid state storage device (SSD). The networkinterface 215 is used by the client system 140 to connect to a wirelessnetworks provided by the access point 120 as well as receive beaconmessages and probe responses sent by the access point 120.

Illustratively, the memory 225 includes a configuration tool 227 andstorage 230 stores network profiles 235. The configuration tool 227 mayprovide software used to access and configure the wireless access point120 (e.g., to define one or more wireless networks exposed on the accesspoint 120). For example, the configuration tool 227 may allow a user tospecify an SSID for the access point (or for multiple, virtual accesspoints) as well as enable security features or configure other aspectsof a wireless network (e.g., firewall rules, DHCP settings, portforwarding, device access imitations etc.). In one embodiment, when auser configures a wireless network on the access point 120, the tool 227may store a network profile 235 used to identify the access point 120 ina variety of scenarios. For example, the network profile 235 may storecomponents of the information element used to identify the access point120 across multiple virtual access points, across a factory reset, oracross changes to the settings of a given wireless networkconfiguration.

Further, as noted above, the configuration tool 227 may use data storedin an information element of a beacon to distinguish one access pointfrom another or to identify an access point despite changes to itsconfiguration that result in modifications to the information broadcastin a beacon message (or probe response). That is, the informationelement provides information related to the device itself independentlyfrom the configuration of the wireless network which the beacon message(or probe response) is associated with. In one embodiment, e.g., theinformation element may contain information specific to the device aswell as information regarding the current context of the device. Forexample, the information element may include a device vendor ID, productID, and a device-unique ID. This information element may also include aversion field used to identify a version of firmware or applicationsrunning on the device. The version field may be useful for discerningdevice compatibility—allowing a configuration tool 227 to enable certainconfiguration features depending on whether they are supported by theaccess point 120. The information element may further include contextspecific information regarding a device's configuration.

As shown, the wireless access point 120 includes firmware 250,management component 255, network configuration 260, data component 265,and access point data 270. The firmware component/processor 205 providesthe executable logic of the access point 120, and the memory/storage 252stores application data and configuration settings used by the accesspoint 120. The firmware component/processor 205 may include anapplication specific integrated circuit, FPGA, or other processingdevice, e.g., a CPU having one or more processing cores, etc. Memory 252may include any combination of volatile and non-volatile memory storageelements, including DRAM, flash memory, SSD storage, or magnetic diskdrives, etc.

The data routing component 265 provides executable logic used to sendand receive network frames to/from client devices (e.g., computingsystem 130 ₂) which associate themselves to a wireless network exposedby the access point 120. For example, the data routing component 265 mayreceive network frames from client 130 ₂ and forward them over theuplink 105 to another network device, e.g., to a broadband router suchas a cable modem). Of course, the wireless access point may beintegrated with other network devices such as a broadband router.

In one embodiment, the management component 255 allows a user toconfigure the access point 120, via the configuration tool 227. Forexample, the configuration tool may allow users to configure (orautomatically configure) a variety of settings on the access point 135such as an SSID value, whether the SSID value is broadcast, networksettings, DHCP settings, firewall settings and the like. The networkconfiguration 260 corresponds to the configuration settings for awireless network (or multiple virtual access points) hosted by theaccess point 120. For example, the network configuration 260 may storethe SSID names and security settings configured by a user via theconfiguration tool 227. Access point data 270 provides the devicespecific information included in an information element broadcast to aclient. For example, access point data 270 may store a vendor, product,and device ID data. Such data may be included in information elementsbroadcast by the access point in beacon messages. Further, access pointdata 270 may also include firmware version data or other contextspecific information regarding the current configured state of theaccess point 120.

FIGS. 3A and 3B illustrate example formats for encoding device databroadcast from a wireless access point in order to identify thatwireless access point, according to one embodiment presented in thisdisclosure. More specifically, FIG. 3A illustrates an example embodimentwhere the information element is encoded in a management frame (e.g., abeacon or probe response) as defined by the IEEE Std 802.11-2007, “IEEEStandard for Information Technology—Telecommunications and informationexchange between systems—Local and metropolitan area network—Specificrequirements—Part 11: Wireless LAN Medium Access Control (MAC) andPhysical Layer (PHY) specifications.” Of course, one of ordinary skillin the art will recognize that the example data formats presented inFIGS. 3A and 3B may be adapted for other versions of the 802.11standard, as well as adapted for use with other wireless protocols orstandards.

As shown, frame 305 provides an example of an information elementencoded using a reserved information element ID. As shown, the frame 305includes an element ID field 305 (used to identify the informationelement) a one byte length field 310, and the device data field 315.Note, while shown as being N bytes in length, the one byte length field310 limits the device data to 255 bytes. In this example embodiment, oneof the element IDs reserved by the IEEE Std 802.11-2007 standard couldbe assigned for use in carrying the device specific information element.

Alternatively, or additionally, frame 320 provides an example of adevice information element encoded in a vendor specific informationelement—as defined by the IEEE Std 802.11-2007. In this example, frame320 defines a format for an information element used to store vendorspecific functionality, identified using a vendor OrganizationallyUnique Identifier (OUI) registered with IEEE. As shown, the element IDfield 321 is set to a hexadecimal value of 0xDD, indicating that theinformation element is a “Vendor Specific Information Element” asdefined in the IEEE Std 802.11-2007. The frame 320 also includes a onebyte length field 322, a 3 byte OUI field 323 used to store theorganizationally unique identifier, a one byte qualifier field 324, andan N-4 byte device data field 325. Note, the maximum size of the devicedata field 325 is slightly smaller in frame 320 as four bytes are neededfor the OUI field 323 and the qualifier field 324.

In frames 305 and 320, the device data field 305, 325 respectively, isused to store the device specific information broadcast with a wirelessaccess point beacon (or probe response). FIG. 3B illustrates an exampleformat for data frames broadcast from a wireless access point in orderto identify that wireless access point, according to one embodimentpresented in this disclosure. More specifically, FIG. 3B illustrates adevice data field 350 which includes a plurality of fields used to storedevice and product data broadcast with a broadcast with a wirelessaccess point beacon. As shown, the device data field 350 includes a onebyte vendor ID length field 351 and a corresponding vendor ID field 353between 1-24 bytes in length. Similarly, the device data field 350includes a one byte product ID length field 353 and a correspondingproduct ID field 354 between 1-24 bytes in length. In addition thevendor and product IDs, the device data field also includes a device IDfield 255 used to store a 16 byte device ID. For a given vendor andproduct, the unique device ID effectively acts as a unique serialnumber.

Further, in addition to the vendor, product, and device ID data, thedevice data field 350 also includes a ten byte version ID field 356, aone byte context ID field 357, and a three byte context variable 358.The version ID field 356 provides a field used to store versioninformation for a given access point. The version information maycorrespond to what version of firmware or routing software (or otherapplication packages or software) have been installed on the wirelessaccess point. Data field 360 provides an example format for version IDfield 356. Illustratively, the version may be represented as a ten bytefield configured using a two byte major version field 361, a two byteminor version field 362, a two byte revision field 363 and a four bytebuild number field 364. Of course, version ID field 356 could be encodedusing a variety of other configurations.

In one embodiment, the context ID field 357 may be used to indicatewhether context information is included in the device data field 350.For example, if no context information is included, then the value ofthe context ID field 357 may be set to zero. A non-zero value indicatesthat the bits in the context field 358 provide actual context,configuration, and/or state data. For example, bits in the context field358 may be used to convey whether the device has been configured or isin a factory default state, whether a given wireless network identifiedin a beacon is a guest network or primary wireless network hosted on anaccess point, whether an uplink from the access point is available, etc.

As a simple example, a lowest bit in the bit context field 358 couldmean the access point has been configured (i.e., is not in a factorydefault state), the second lowest bit could indicate whether the beaconis for a guest or primary network on the access point, and the thirdlowest bit could indicate whether the access point currently hasWAN/internet access (for the network corresponding to the beacon). Otherbits in the context field 358 could indicate whether the access point(or network corresponding to the beacon) supported a variety ofdifferent features or network services, e.g., geolocation or QRcodeservices. Similarly, a byte of the 3-byte context field 358 could beused to indicate a current router load or available radio bandwidthcoupled with available upstream internet speed, etc. For example, an 8bit field could be used to indicate current router load, with 0 meaningno load information, and 1-255 for increasing amounts of radio bandwidthand upstream internet speeds available.

Again, while FIGS. 3A and 3B illustrate data formats that allow vendor,device, product, and context information to be integrated withmanagement frames broadcasting beacon (and probe response) messagesconfigured using the 802.11 network standards, embodiments presentedherein may readily be adapted for use with other wireless networkingstandards, protocols, or approaches.

FIG. 4 illustrates a method 400 for a wireless access point to broadcastframes used to identify that wireless access point, according to oneembodiment presented in this disclosure. As shown, the method 400 beginsat step 405 where an access point determines a current configurationstatus of a wireless network on a wireless access point. For example,the access point may provide multiple wireless networks in differentradio frequencies. In such a case, when the access point generates abeacon message for one of the wireless networks, e.g., firmwareexecuting on that access point may determine the configuration status ofthat network.

At step 410, the firmware may generate an information element whichincludes the configuration status and the device ID to include in thebeacon message to be broadcast by that access pint for a given wirelessnetwork. Such a beacon may be broadcast for each virtual access pointconfigured on a given device. Similarly, the firmware may determine thecurrent configuration status and device ID information to include in aninformation element included in a probe response message. Oncegenerated, at step 415, the access point broadcasts the beacon (or proberesponse) message, where it may be observed by any clients within rangeof the access point.

As noted, the access point may broadcast a beacon at regular intervals.Accordingly, at step 420, the access point waits until the time intervalhas elapsed. The method then returns to step 405, where the access pointgenerates and broadcasts a new beacon message. Advantageously, includingthe information element described herein in beacon messages and proberesponses allows client software to determine that a common physicaldevice is being used to host multiple access points or to identify adevice across a factory reset or across a variety of different changesto the configuration settings of that device.

As will be appreciated by one skilled in the art, embodiments presentedin this disclosure may be implemented as a system, method or computerprogram product. Accordingly, embodiments presented herein may beimplemented as an entirely hardware embodiment, as an entirely softwareembodiment (including firmware, resident software, micro-code, etc.) oran embodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present disclosure may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus or device.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality and operation of possible implementations ofsystems, methods and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

While the foregoing is directed to embodiments of the presentdisclosure, other and further embodiments may be devised withoutdeparting from the basic scope thereof. In view of the foregoing, thescope of the present disclosure is determined by the claims that follow.

We claim:
 1. A method, comprising: exposing, on a wireless access pointdevice, at least a first wireless network hosted by a first virtualaccess point configured on the wireless access point device and a secondwireless network hosted by a second virtual access point configured onthe wireless access point device; generating a first management framecorresponding to the first wireless network and a second managementframe corresponding to the second wireless network, wherein the firstand second management frames each include an information element storinga plurality of information fields, the information fields storingidentification information identifying the wireless access point deviceindependently from both a configuration of the first and second wirelessnetworks and a first and second Media Access Control (MAC) addressassociated with the first and second virtual access points,respectively, and wherein at least a first one of the information fieldsidentify the wireless access point device hosting the first and secondvirtual access points; and broadcasting the first and second managementframes to one or more client devices within range of the wireless accesspoint.
 2. The method of claim 1, wherein the first and second managementframes are beacon messages broadcast to identify the first and secondwireless networks exposed, respectively, by the first and second virtualaccess points to the one or more client devices.
 3. The method of claim1, further comprising: receiving, on the first virtual access point, aprobe request message, wherein the first management frame is generatedand broadcast in response to the probe request message.
 4. The method ofclaim 1, wherein the plurality of information fields include an accesspoint vendor field, an access point product field and an access pointdevice ID field.
 5. The method of claim 1, wherein the plurality ofinformation fields include an access point version field.
 6. The methodof claim 1, wherein the plurality of information fields include anaccess point device context field.
 7. The method of claim 6, wherein theaccess point device context field identifies whether the first wirelessnetwork has either a default device configuration state or a userconfigured state.
 8. The method of claim 6, wherein the access pointdevice context field identifies whether the first wireless network is aguest wireless network or a primary wireless network.
 9. Anon-transitory computer-readable storage medium storing code forexecution by a wireless access point, wherein the code, when executed bythe wireless access point, performs an operation, comprising: exposing,on a wireless access point device, at least a first wireless networkhosted by a first virtual access point configured on the wireless accesspoint device and a second wireless network hosted by a second virtualaccess point configured on the wireless access point device; generatinga first management frame corresponding to the first wireless network anda second management frame corresponding to the second wireless network,wherein the first and second management frames each include aninformation element storing a plurality of information fields, theinformation fields storing identification information identifying thewireless access point device independently from both a configuration ofthe first and second wireless networks and a first and second MediaAccess Control (MAC) address associated with the first and secondvirtual access points, respectively, and wherein at least a first one ofthe information fields identify the wireless access point device hostingthe first and second virtual access points; and broadcasting the firstand second management frames to one or more client devices within rangeof the wireless access point.
 10. The non-transitory computer-readablestorage medium of claim 9, wherein the first and second managementframes are beacon messages broadcast to identify the first and secondwireless networks exposed, respectively, by the first and second virtualaccess points to the one or more client devices.
 11. The non-transitorycomputer-readable storage medium of claim 9, wherein the operationfurther comprises: receiving, on the first virtual access point, a proberequest message, wherein the first management frame is generated andbroadcast in response to the probe request message.
 12. Thenon-transitory computer-readable storage medium of claim 9, wherein theplurality of information fields include an access point vendor field, anaccess point product field and an access point device ID field.
 13. Thenon-transitory computer-readable storage medium of claim 9, wherein theplurality of information fields further include an access point versionfield.
 14. The non-transitory computer-readable storage medium of claim9, wherein the plurality of information fields include an access pointdevice context field.
 15. The computer-readable storage medium of claim14, wherein the access point device context field identifies whether thefirst wireless network has either a default device configuration stateor a user configured state.
 16. The non-transitory computer-readablestorage medium of claim 14, wherein the access point device contextfield identifies whether the first wireless network is a guest wirelessnetwork or a primary wireless network.
 17. An apparatus, comprising: aprocessor; and a memory storing executable instructions which, whenexecuted on the processor, perform an operation, comprising: exposing,on a wireless access point device, at least a first wireless networkhosted by a first virtual access point configured on the wireless accesspoint device and a second wireless network hosted by a second virtualaccess point configured on the wireless access point device, generatinga first management frame corresponding to the first wireless and asecond management frame corresponding to the second wireless network,wherein the first and second management frames each include aninformation element storing a plurality of information fields, theinformation fields storing identification information identifying thewireless access point device independently from both a configuration ofthe first and second wireless networks and a first and second MediaAccess Control (MAC) address associated with the first and secondvirtual access points associated with the first and second virtualaccess points, respectively, and wherein at least a first one of theinformation fields identify the wireless access point device hosting thefirst and second virtual access points, and broadcasting the first andsecond management frames to one or more client devices within range ofthe wireless access point.
 18. The apparatus of claim 17, wherein thefirst and second management frames are beacon messages broadcast toidentify the first and second wireless networks exposed, respectively,by the first and second virtual access points to the one or more clientdevices.
 19. The apparatus of claim 17, wherein the operation furthercomprises: receiving, on the first virtual access point, a probe requestmessage, wherein the first management frame is generated and broadcastin response to the probe request message.
 20. The apparatus of claim 17,wherein the plurality of information fields include an access pointvendor field, an access point product field and an access point deviceID field.
 21. The apparatus of claim 17, wherein the plurality ofinformation fields further include an access point version field. 22.The apparatus of claim 17, wherein the plurality of information fieldsinclude an access point device context field.
 23. The apparatus of claim22, wherein the access point device context field identifies whether thefirst wireless network has either a default device configuration stateor a user configured state.
 24. The apparatus of claim 22, wherein theaccess point device context field identifies whether the first wirelessnetwork is a guest wireless network or a primary wireless network. 25.The apparatus of claim 22, wherein the context field identifies one ormore network services supported by the first wireless network.
 26. Theapparatus of claim 22, wherein the context field identifies an uplinkstate for the first wireless network exposed on the wireless accesspoint device.
 27. The apparatus of claim 22, wherein the context fieldidentifies at least one of a current load or an available radiobandwidth for the first wireless network exposed on the wireless accesspoint device.